Enabling IP carrier peering

ABSTRACT

Methods and systems may provide carrier ENUM based routing for subscriber devices (e.g., voice or other multimedia services over IP) to locate and to connect to subscriber devices of another IP peering carrier. A private ENUM database may be used to connect subscribers of disparate carriers using a domain for designated breakout gateway control functions.

TECHNICAL FIELD

The technical field generally relates to providing communication services and, more specifically, to systems and methods for Internet Protocol (IP) connections between IP carriers.

BACKGROUND

A large number of connections between devices, such as telephone calls, are now being carried via packet-switched networks. IP networks have evolved to allow users to send voice and data, including telephone calls, through packet-switched networks, such as the Internet, instead of through older networks like the PSTN. Accordingly, networks often utilize the Internet Protocol (IP), which is the basic transmission protocol used for Internet communications, to form these connections. For carriers to provide service to subscribers by using IP networks, however, it is necessary for networks to interconnect so that their subscribers can connect to each other.

Providing such interconnection generally involves a mechanism by which calls that are intended for disparate networks are sent through egress routing nodes of one network to gateway nodes of other networks. To the extent that one of the available networks recognizes that the destination device resides on it, the network will take steps to route the call to the destination device.

A problem exists, however, in that neither the originating network nor the recipient networks have insight into the eventual call path. When the originating network detects initiation of call intended for a device on another network, it does not necessarily know the identity or the routing information of the recipient device. Accordingly, it must send call information to available networks and rely on the intended recipient network to take steps to complete the call. Similarly, the recipient network has no idea when or if a particular call initiated on another network will be intended for it. Accordingly, it must “listen” for all calls initiated by all available networks to insure that it does not miss a call that may be intended for a subscriber. This approach is costly because it expends system resources on the originating side by sending call requests to available networks regardless of whether all such networks are actually recipients and expends resources on the recipient side by requiring the monitoring of call requests by networks that are not intended recipients. Therefore, what is needed is an approach for efficient use of system resources while providing IP carrier interconnection.

SUMMARY

Disclosed herein are methods and systems which provide carrier ENUM based routing for subscriber devices (e.g., voice or other multimedia services over IP) to locate and to connect to subscriber devices of another IP peering carrier. For example, a private ENUM may be used to more efficiently connect subscribers of disparate carriers.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale.

FIG. 1 illustrates an exemplary system for implementing carrier ENUM.

FIG. 2A illustrates an exemplary flow diagram of processing an IP based call (e.g., VoLTE (voice over long term evolution)) from a first subscriber of a first carrier to a second subscriber of the first carrier or to a second subscriber of a second carrier;

FIG. 2B illustrates a continuation of flow in FIG. 2A of an exemplary processing an IP based call from first subscriber of a first carrier to second subscriber of a second carrier;

FIG. 3 illustrates a schematic of an exemplary network device.

FIG. 4 illustrates an exemplary communication system that provides wireless telecommunication services over wireless communication networks.

FIG. 5 illustrates an exemplary communication system that provides wireless telecommunication services over wireless communication networks.

FIG. 6 illustrates an exemplary telecommunications system in which the disclosed methods and processes may be implemented.

FIG. 7 illustrates an example system diagram of a radio access network and a core network.

FIG. 8 depicts an overall block diagram of an example packet-based mobile cellular network environment, such as a general packet radio service (GPRS) network.

FIG. 9 illustrates an exemplary architecture of a GPRS network.

FIG. 10 is a block diagram of an exemplary public land mobile network (PLMN).

DETAILED DESCRIPTION

ENUM (tElephone NUmber Mapping) is a suite of protocols and architecture designed by the Internet Engineering task force to unify the E.164 telephone numbering system with the IP addressing system. The present disclosure will not provide an in-depth description of the ENUM standard, but will focus on the subject matter needed to describe the principles set forth herein. Nevertheless, an exemplary description of ENUM terminology, protocols, and infrastructure can be found in U.S. Pat. No. 8,792,481, entitled “Methods, systems, and computer program products for providing inter-carrier IP-based connections using a common telephone number mapping architecture”, which is hereby incorporated by reference in its entirety.

One characteristic of ENUM is a hierarchy of databases that are used by networks to identify routing information to establish connections between the various devices that are residing thereon. A multiple-tiered database structure is used to provide carriers with the ability to form connections between various devices without necessarily sharing network architecture and routing information.

Carriers using ENUM have access to an indirect lookup method to obtain Naming Authority Pointer Resource (NAPTR) records associated with various devices residing on other networks. A NAPTR record is received from a network-based Domain Name System (DNS) and is indexed on the E.164 telephone number of a device. A NAPTR record includes, among other things, information that designates how and where a device can be contacted. For example, a NAPTR record may designate what types of communications a device can establish, such as a VoIP connection using Session Initiation Protocol (SIP), a voice connection using the E.164 telephone number, a short message service (SMS) or multimedia message service (MMS) session, etc. The NAPTR may provide a uniform resource identifier (URI) that identifies how to contact the terminal to use a selected service, and may designate a priority for each of the various connection methods. ENUM infrastructure includes a plurality of tiered databases that are utilized to locate subscriber devices on the various networks making up the infrastructure. For the purposes of the present disclosure, one such database will now be described.

A private ENUM database generally provides routing information for subscribers within a single network operated by a particular communication service provider. If a request is received from an originating device on a network to call a device having a particular number, the network will first check the private ENUM database. If the number resides in the private ENUM database, then the recipient device also resides on the network and the two devices may be connected. If the private ENUM database does not have a record for the number, then it is understood that the recipient device resides on an external carrier network or the recipient device does not belong to one of the IP end points of the same carrier (e.g., 3G or PSTN).

Disclosed herein are methods and systems which utilize a private ENUM database that may enhance an originating network's ability to provide carrier ENUM based routing for subscribers (e.g., voice or other multimedia services over IP) to locate and to connect to subscribers of another IP peering carrier. For example, a private ENUM may be used to more efficiently connect subscribers of disparate carriers.

FIG. 1 illustrates an exemplary system that may enhance a carrier ENUM capability via use of a private ENUM server. Device 101 (e.g., portable digital assistants (PDAs), laptop computers, tablet devices and other mobile devices, such as cellular telephones, smart appliances, and so on) may attempt to connect to device 102 (e.g., mobile phone). It assumed, in this scenario, that device 101 and device 102 (also referred herein as subscriber 101 and subscriber 102, respectively) are on disparate carrier networks, a first carrier network and a second carrier network. At step 201, after originating processing is complete, calls are routed to terminating serving call session control function (S-CSCF) 222 (e.g., an intra-network routing function). At step 202, S-CSCF 222 initiates a private ENUM query to a private ENUM database 221 (also known herein as private ENUM 221).

At step 203, private ENUM 221 matches a “foreign” destination number or number range and returns T1ENUM_1.firstnetwork.net domain, as an example. Foreign in this context means a number or number range that is not assigned to the first carrier's subscribers; it does not necessarily refer to an International number or number range. It is contemplated herein that in addition to provisioning first carrier telephone numbers in the private ENUM, there is provisioning of other numbers (e.g., NPAs, international country codes, national number ranges, combinations thereof, etc.) associated with the second carrier or multiple additional carriers, including carriers reached via 3^(rd) party hubbing carriers such as IP Exchange (IPX) carriers. The first carrier is provisioning non-first carrier numbers in the private ENUM and having it return a new domain(s) that may be used as criteria to direct the carrier ENUM query (e.g., step 208 discussed in more detail herein) to one of several possible Tier 0/1 ENUM providers. Furthermore, the returned domain(s) may be used as a means for the first carrier to direct the call to specific subsets of network equipment which may provide optimizations in call routing, such as reducing call setup or media delay, providing specific network functions (e.g., routing the call to equipment that is enabled to perform Carrier ENUM queries), reducing network costs, or other optimizations.

For additional perspective before referring to step 204, conventionally a private ENUM only contains subscriber telephone numbers of the first carrier. Since the destination of the call is to a telephone number (TN) owned by another carrier (second carrier), conventionally there is no private ENUM match and it just returns NXDOMAIN (non-existent domain). Conventionally, there is no query of a private DNS server or the like as discussed in more detail herein. Also, conventionally, without carrier ENUM, 1) an S-CSCF would determine the call needs to route to the PSTN (via breakout gateway control function (BGCF)) due to receiving NXDOMIAN from Private ENUM response; 2) S-CSCF sends call to a BGCF; and 3) BGCF routes call to the PSTN.

With continued reference to FIG. 1, at step 204, S-CSCF 222 determines T1ENUM_1.firstnetwork.net domain fully qualified domain name (FQDN) maps to new bgcfpool1.firstnetwork.net FQDN. As discussed below this step may be skipped. A fully qualified domain name (FQDN), sometimes also referred to as an absolute domain name, is a domain name that specifies its location in the tree hierarchy of the Domain Name System (DNS). Different S-CSCFs may map the common T1ENUM_1.firstnetwork.net to different bgcfpool<x>.firstnetwork.fqdns. At step 205, S-CSCF 222 sends a query to DNS server 223 to resolve bgcfpool1.firstnetwork.net FQDN. It is not required that S-CSCF 222 maps the received T1ENUM_1.firstnetwork.net domain to another FQDN (e.g. bgcfpool1.firstnetwork.net) prior to performing the DNS query at step 204 and step 205. S-CSCF 222 may instead choose to resolve the received T1ENUM_1.firstnetwork.net domain. The possible mapping of bgcfpool1.firstnetwork.net in step 204 and step 205 may provide further flexibility in DNS resolution. For example, different S-CSCFs 222 may map bgcfpool1.firstnetwork.net to different FQDNs, thereby choosing different BGCFs as the next hop. This may be useful in reducing network delays allowing S-CSCFs to choose BGCFs that are geographically local to each other.

At step 206, DNS server 223 resolves bgcfpool1.firstnetwork.net FQDN with an IP address to a ENUM-enabled BGCF 224 (a subset of BGCFs of first carrier), which is received by S-CSCF 222. The destination telephone numbers that the first carrier would initiate a Carrier ENUM query for could be directed to a “subset” of the BGCFs in the network (there may be one or more BGCFs), which would limit the need to only equip a subset of BGCFs with the Carrier ENUM client capability. Calls for the non-first carrier telephone numbers that may use ENUM may be directed to a specific set of BGCFs 224. For additional perspective, it is significant to understand that conventionally when an S-CSCF receives a call destined for an external network, (e.g., another carrier), the S-CSCF typically distributes the call among the BGCFs in the first carrier network (e.g., all the BGCFs). As such, all of the BGCFs in the network would need to support the ability to initiate carrier ENUM queries, even if the call did not require a carrier ENUM query. By using the bgcfpool1.firstnetwork.net (or T1ENUM_1.firstnetwork.net) FQDN for calls that do require a carrier ENUM query, this allows the call to be routed to a limited set of ENUM-enabled BGCFs, thereby reducing the number of BGCFs that must be equipped to support carrier ENUM.

At step 207, S-CSCF 222 routes calls to the ENUM-enabled BGCFs 224 (subset of BGCFs) based on DNS server 223 response of step 206. Calls that do not require carrier ENUM, such as calls that returned an NXdomain at step 203 or at step 206, may be routed to those BGCFs 225 that are not equipped with ENUM client. At step 208, carrier ENUM is supported, therefore BGCF 224 determines that a carrier ENUM query should be performed, such as to a Tier 0/1 ENUM server. Carrier ENUM client of BGCF 224 (which may or may not be integrated with BGCF) initiates a query and receives a response, which may be to or from a Tier 0/1 ENUM server. BGCF 224 may act like an ENUM client, therefore it may query to Tier 0/1 ENUM provider database. The following is an exemplary query: ORIGIN 3.8.0.0.6.9.2.3.6.4.1.e164enum.net. At step 209, BGCF 224 routes call based upon carrier ENUM query response of step 208 and other routing logic.

With continued reference to the scenario in FIG. 1, it should be understood that private ENUM 221 may match on foreign numbers (foreign in this context means not a home-network subscriber, not necessarily International). Private ENUM 221 typically just contains home-network numbers. A match on these non-home network destinations by private ENUM 221 may indicate that a carrier ENUM query should be performed. Furthermore, unique domains may be provisioned for different foreign number ranges to be used as pointers to multiple Tier 0/1 ENUM servers. For example, Tier1ENUM1 may be used for calls to NumberRange1 (e.g., a first number range) and Tier1ENUM2 for calls to NumberRange2 (a second number range), etc. Step 204 may be skipped if T1ENUM_1.firstnetwork.net domain provides information needed to route the call appropriately. But as shown, at step 204, bgcfpool1.firstnetwork.net domain may be used to further control which BGCFs (e.g., carrier ENUM clients) should be selected by S-CSCF 222. For example, S-CSCF 222 may route to regional BGCFs, based on the call's originating or terminating location. If step 204 is not performed, the original T1ENUM_1.firstnetwork.net FQDN may be resolved in step 205 and step 206. It is contemplated herein that T1ENUM_1.firstnetwork.net and the others are just exemplary domains and other domain that serve the same function may be used.

The Private ENUM mapping of foreign number ranges to unique FQDNs may provide multiple capabilities. A first capability allows for the indication of which destinations may use carrier ENUM to determine the terminating network. A second capability, is that because the determination of which destinations may use Carrier ENUM is made prior to the external network routing function that contains the carrier ENUM client (e.g., BGCF), the intra-network routing function (e.g., S-CSCF) may now direct the calls that would initiate a carrier ENUM query to those BGCFs enabled to perform the carrier ENUM query. This may allow a network provider to not have to equip all BGCFs to support a carrier ENUM client. A third capability may be the use of different FQDNs within the private ENUM for different destination number ranges to choose among a plurality of Tier 0/1 ENUM providers. For example, calls to a given country code may be routed to a subset of carrier ENUM clients (BGCFs) that are enabled to contact Tier 0/1 ENUM Provider #1, whereas calls to Country Code #2 could be routed to a subset of carrier ENUM Clients (BGCFs) that are enabled to contact Tier 0/1 ENUM Provider #2.

It is contemplated herein that the disclosed subject matter, although in IMS terms (e.g., S-CSCF, BGCF) applies to other network architectures (e.g., it doesn't have to be IMS). S-CSCF 222 may be similar to a generic intra-network routing function. As disclosed, S-CSCF 222 may be the Private ENUM query and make routing decisions on which BGCF to select. BGCFs 224 or BGCF 225 may be considered a generic, inter-network (i.e., external) routing function (the function determines how to best route a call to another network).

IPX eligible calls are calls that may be processed by the carrier ENUM enabled BGCFs to launch the InterCarrier Tier 0/1 ENUM query to the Tier 0/1 ENUM vendor (IPX in this case). An IP exchange (IPX) network in one example is generally a network operated by a plurality of network carriers to provide for inter-network exchange of data between carriers. CC1 is one example of Tier 1. Other CC can also be Tier 1. For example, CC 44 (UK) is another example of Tier 1. A Tier 1 registry normally covers all the numbers in a country. Tier 0 may include delegations to Tier 1 registries based on country code . . . . As disclosed herein, it is not restricted to Tier 1 ENUM server, it may be Tier 0/1, if all other international carriers opt in to the Carrier ENUM of a carrier, for example.

FIG. 2A, illustrates an exemplary flow diagram of processing an IP based call (e.g., VoLTE (voice over long term evolution)) from a first subscriber of a first carrier to a second subscriber of the first carrier or to a second subscriber of a second carrier (FIG. A-FIG. 2B). At step 241, an IP call from first subscriber 101 of first carrier, intended for another subscriber of first carrier (not shown) or second subscriber 102 of second carrier, is received. The call (a request to connect the first subscriber to another subscriber of first carrier or the second subscriber) is received by S-CSCF 222 and sent to private ENUM 221. The request may include an e-164 request. At step 242, private ENUM 221 receives a first ENUM query with domain “e164.arpa.” At step 243, private ENUM 221 determines which SIP URI (Session Initiation Protocol Uniform Resource Identifier), if any, is applicable for the ENUM, which may be 10-digit number or appropriate variation thereof (e.g., country code) is stored within private ENUM 221. If an SIP URI of home.firstcarrier.net is retrieved (Yes), it indicates that the second user is also a subscriber to the first network. Therefore, in step 244, at S-CSCF 222 performs DNS look-up to resolve a domain name to IP address and completes the call (IP-to-IP) in step 245. However, if an SIP URI is not retrieved (No) or T1ENUM_1.firstnetwork.net is retrieved, it indicates that second subscriber 102 is not a subscriber to the first carrier network. In a first scenario T1ENUM_1.firstnetwork.net is retrieved and further processing is done as continued in flow A 250 of FIG. 2B. In a second scenario, where there is no SIP URI retrieved then the call may be routed to BGCF for the PSTN to process.

FIG. 2B illustrates a continuation of flow in FIG. 2A of an exemplary processing an IP based call from first subscriber 101 of a first carrier to second subscriber 102 of a second carrier. At step 243 of FIG. 2B, there is additional considerations by private ENUM 221. Private ENUM 221 determines whether the ENUM has an entry for a number or number range that is not of the first carrier that corresponds to a domain (e.g., T1ENUM_1.firstnetwork.net). If yes, then the process proceeds to step 246. At step 246, DNS server 223 based on T1ENUM_1.firstnetwork.net (or subsequent remapping to bgcfpool1.firstnetwork.net as disclosed above) provides the next hop FQDN that point to selected ENUM-enabled BGCFs 224 (subset of BGCFs in first carrier network). At step 247, S-CSCF 222 sends the traffic to a selected ENUM-enabled BGCFs 224. At step 248, BGCF 224 sends revised ENUM queries to Tier 1 ENUM server based on DNS server 223 (which may be a private DNS server) record information of Tier 0/1 IP address. A Tier 0/1 ENUM server may provide name server (NS) records that provide routing information that is known to the Tier 0/1 database, but is not known to a private ENUM database (or server). For example, a Tier 0/1 ENUM server may identify network databases of other networks, which are known to the Tier 0/1 ENUM servers along with ranges of numbers managed by these servers. These other servers are referred to as Tier 2 ENUM servers. Accordingly, a Tier 0/1 ENUM server may provide the name of a network and a Tier 2 ENUM server that manages a number associated with a particular device. The originating network may then contact the appropriate Tier 2 ENUM server to receive information needed to complete a call. For further details with regard to this Tier 0/1 ENUM server query (e.g., step 208), among other things, see U.S. patent application Ser. No. 15/222,337, entitled “Methods and Target Architecture for Enabling IP Carrier Peering,” which is hereby incorporated by reference in its entirety.

With continued reference to FIG. 2B, if no at step 243, then at step 251 the next hope FQDN points to the general pool of BGCFs, which may not be ENUM enabled. At step 252, S-CSCF 222 sends the traffic to BGCFs. At step 253, the call may be routed to the PSTN or 2G or 3G network.

Disclosed herein are methods and systems to enable a private ENUM to respond to a telephone number of a different carrier. Conventionally, when detecting a non-carrier TN a private ENUM may abandon the call in an IP way and switch it to the PSTN. Also, conventionally ENUM would include the full telephone string. However, disclosed herein, a country code, a NPA (e.g., NPA 416), or subset of digits of the TN may be used to direct calls to a subset of BGCFs, which may allow for more efficient processing of the call. For example, a call to a specific country code, or particular provider associated Country Code/National Number range is detected, then the call may be routed to BGCFs that more efficiently process calls destined to that country or number range. The components herein may be logical network components. For example, BGCFs may be considered a routing function for a call. In another example, functions of the BGCF and S-CSCF may be integrated into one device or distributed across multiple devices. Note that one possible advantage of reducing the number of BGCFs that must be equipped to support carrier ENUM, is reducing costs that occur for having such functions enabled (e.g., cost for updating or maintaining software, licensing fees, etc.).

FIG. 3 is a block diagram of network device 300 that may be connected to or comprise a component of the network of FIG. 1. Network device 300 may comprise hardware or a combination of hardware and software. The functionality to facilitate telecommunications via a telecommunications network may reside in one or combination of network devices 300. Network device 300 depicted in FIG. 3 may represent or perform functionality of an appropriate network device 300, or combination of network devices 300, such as, for example, a component or various components of a cellular broadcast system wireless network, a processor, a server, a gateway, a node, a mobile switching center (MSC), a short message service center (SMSC), an automatic location function server (ALFS), a gateway mobile location center (GMLC), a radio access network (RAN), a serving mobile location center (SMLC), or the like, or any appropriate combination thereof. It is emphasized that the block diagram depicted in FIG. 3 is exemplary and not intended to imply a limitation to a specific implementation or configuration. Thus, network device 300 may be implemented in a single device or multiple devices (e.g., single server or multiple servers, single gateway or multiple gateways, single controller or multiple controllers). Multiple network entities may be distributed or centrally located. Multiple network entities may communicate wirelessly, via hard wire, or any appropriate combination thereof.

Network device 300 may comprise a processor 302 and a memory 304 coupled to processor 302. Memory 304 may contain executable instructions that, when executed by processor 302, cause processor 302 to effectuate operations associated with mapping wireless signal strength. As evident from the description herein, network device 300 is not to be construed as software per se.

In addition to processor 302 and memory 304, network device 300 may include an input/output system 306. Processor 302, memory 304, and input/output system 306 may be coupled together (coupling not shown in FIG. 3) to allow communications between them. Each portion of network device 300 may comprise circuitry for performing functions associated with each respective portion. Thus, each portion may comprise hardware, or a combination of hardware and software. Accordingly, each portion of network device 300 is not to be construed as software per se. Input/output system 306 may be capable of receiving or providing information from or to a communications device or other network entities configured for telecommunications. For example input/output system 306 may include a wireless communications (e.g., 3G/4G/GPS) card. Input/output system 306 may be capable of receiving or sending video information, audio information, control information, image information, data, or any combination thereof. Input/output system 306 may be capable of transferring information with network device 300. In various configurations, input/output system 306 may receive or provide information via any appropriate means, such as, for example, optical means (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi, Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone, ultrasonic receiver, ultrasonic transmitter), or a combination thereof. In an example configuration, input/output system 306 may comprise a Wi-Fi finder, a two-way GPS chipset or equivalent, or the like, or a combination thereof.

Input/output system 306 of network device 300 also may contain a communication connection 308 that allows network device 300 to communicate with other devices, network entities, or the like. Communication connection 308 may comprise communication media. Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, or wireless media such as acoustic, RF, infrared, or other wireless media. The term computer-readable media as used herein includes both storage media and communication media. Input/output system 306 also may include an input device 310 such as keyboard, mouse, pen, voice input device, or touch input device. Input/output system 306 may also include an output device 312, such as a display, speakers, or a printer.

Processor 302 may be capable of performing functions associated with telecommunications, such as functions for processing broadcast messages, as described herein. For example, processor 302 may be capable of, in conjunction with any other portion of network device 300, determining a type of broadcast message and acting according to the broadcast message type or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having a concrete, tangible, physical structure. As is known, a signal does not have a concrete, tangible, physical structure. Memory 304, as well as any computer-readable storage medium described herein, is not to be construed as a signal. Memory 304, as well as any computer-readable storage medium described herein, is not to be construed as a transient signal. Memory 304, as well as any computer-readable storage medium described herein, is not to be construed as a propagating signal. Memory 304, as well as any computer-readable storage medium described herein, is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction with telecommunications. Depending upon the exact configuration or type of processor, memory 304 may include a volatile storage 314 (such as some types of RAM), a nonvolatile storage 316 (such as ROM, flash memory), or a combination thereof. Memory 304 may include additional storage (e.g., a removable storage 318 or a non-removable storage 320) including, for example, tape, flash memory, smart cards, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, USB-compatible memory, or any other medium that can be used to store information and that can be accessed by network device 300. Memory 304 may comprise executable instructions that, when executed by processor 302, cause processor 302 to effectuate operations to map signal strengths in an area of interest.

FIG. 4 illustrates a functional block diagram depicting one example of an LTE-EPS network architecture 400 related to the current disclosure. In particular, the network architecture 400 disclosed herein is referred to as a modified LTE-EPS architecture 400 to distinguish it from a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in part on standards developed by the 3rd Generation Partnership Project (3GPP), with information available at www.3gpp.org. In one embodiment, the LTE-EPS network architecture 400 includes an access network 402, a core network 404, e.g., an EPC or Common BackBone (CBB) and one or more external networks 406, sometimes referred to as PDN or peer entities. Different external networks 406 can be distinguished from each other by a respective network identifier, e.g., a label according to DNS naming conventions describing an access point to the PDN. Such labels can be referred to as Access Point Names (APN). External networks 406 can include one or more trusted and non-trusted external networks such as an internet protocol (IP) network 408, an IP multimedia subsystem (IMS) network 410, and other networks 412, such as a service network, a corporate network, or the like.

Access network 402 can include an LTE network architecture sometimes referred to as Evolved Universal mobile Telecommunication system Terrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial Radio Access Network (E-UTRAN). Broadly, access network 402 can include one or more communication devices, commonly referred to as UE 414, and one or more wireless access nodes, or base stations 416 a, 416 b. During network operations, at least one base station 416 communicates directly with UE 414. Base station 416 can be an evolved Node B (eNB), with which UE 414 communicates over the air and wirelessly. UEs 414 can include, without limitation, wireless devices, e.g., satellite communication systems, portable digital assistants (PDAs), laptop computers, tablet devices and other mobile devices (e.g., cellular telephones, smart appliances, and so on). UEs 414 can connect to eNBs 416 when UE 414 is within range according to a corresponding wireless communication technology.

UE 414 generally runs one or more applications that engage in a transfer of packets between UE 414 and one or more external networks 406. Such packet transfers can include one of downlink packet transfers from external network 406 to UE 414, uplink packet transfers from UE 414 to external network 406 or combinations of uplink and downlink packet transfers. Applications can include, without limitation, web browsing, VoIP, streaming media and the like. Each application can pose different Quality of Service (QoS) requirements on a respective packet transfer. Different packet transfers can be served by different bearers within core network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to route packets, e.g., IP traffic, between a particular gateway in core network 404 and UE 414. A bearer refers generally to an IP packet flow with a defined QoS between the particular gateway and UE 414. Access network 402, e.g., E UTRAN, and core network 404 together set up and release bearers as required by the various applications. Bearers can be classified in at least two different categories: (i) minimum guaranteed bit rate bearers, e.g., for applications, such as VoIP; and (ii) non-guaranteed bit rate bearers that do not require guarantee bit rate, e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various network entities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422, Policy and Charging Rules Function (PCRF) 424 and PGW 426. In one embodiment, MME 418 comprises a control node performing a control signaling between various equipment and devices in access network 402 and core network 404. The protocols running between UE 414 and core network 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 and PGW 426, and so on, can be server devices, but may be referred to in the subject disclosure without the word “server.” It is also understood that any form of such servers can operate in a device, system, component, or other form of centralized or distributed hardware and software. It is further noted that these terms and other terms such as bearer paths and/or interfaces are terms that can include features, methodologies, and/or fields that may be described in whole or in part by standards bodies such as the 3GPP. It is further noted that some or all embodiments of the subject disclosure may in whole or in part modify, supplement, or otherwise supersede final or proposed standards published and promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW 420 routes and forwards all user data packets. SGW 420 also acts as a mobility anchor for user plane operation during handovers between base stations, e.g., during a handover from first eNB 416 a to second eNB 416 b as may be the result of UE 414 moving from one area of coverage, e.g., cell, to another. SGW 420 can also terminate a downlink data path, e.g., from external network 406 to UE 414 in an idle state, and trigger a paging operation when downlink data arrives for UE 414. SGW 420 can also be configured to manage and store a context for UE 414, e.g., including one or more of parameters of the IP bearer service and network internal routing information. In addition, SGW 420 can perform administrative functions, e.g., in a visited network, such as collecting information for charging (e.g., the volume of data sent to or received from the user), and/or replicate user traffic, e.g., to support a lawful interception. SGW 420 also serves as the mobility anchor for interworking with other 3GPP technologies such as universal mobile telecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states: detached, idle, or active. The detached state is typically a transitory state in which UE 414 is powered on but is engaged in a process of searching and registering with network 402. In the active state, UE 414 is registered with access network 402 and has established a wireless connection, e.g., radio resource control (RRC) connection, with eNB 416. Whether UE 414 is in an active state can depend on the state of a packet data session, and whether there is an active packet data session. In the idle state, UE 414 is generally in a power conservation state in which UE 414 typically does not communicate packets. When UE 414 is idle, SGW 420 can terminate a downlink data path, e.g., from one peer entity 406, and triggers paging of UE 414 when data arrives for UE 414. If UE 414 responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE 414. For example, HSS 422 can store information such as authorization of the user, security requirements for the user, quality of service (QoS) requirements for the user, etc. HSS 422 can also hold information about external networks 406 to which the user can connect, e.g., in the form of an APN of external networks 406. For example, MME 418 can communicate with HSS 422 to determine if UE 414 is authorized to establish a call, e.g., a voice over IP (VoIP) call before the call is established.

PCRF 424 can perform QoS management functions and policy control. PCRF 424 is responsible for policy control decision-making, as well as for controlling the flow-based charging functionalities in a policy control enforcement function (PCEF), which resides in PGW 426. PCRF 424 provides the QoS authorization, e.g., QoS class identifier and bit rates that decide how a certain data flow will be treated in the PCEF and ensures that this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more of the external networks 406. In illustrative network architecture 400, PGW 426 can be responsible for IP address allocation for UE 414, as well as one or more of QoS enforcement and flow-based charging, e.g., according to rules from the PCRF 424. PGW 426 is also typically responsible for filtering downlink user IP packets into the different QoS-based bearers. In at least some embodiments, such filtering can be performed based on traffic flow templates. PGW 426 can also perform QoS enforcement, e.g., for guaranteed bit rate bearers. PGW 426 also serves as a mobility anchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be various bearer paths/interfaces, e.g., represented by solid lines 428 and 430. Some of the bearer paths can be referred to by a specific label. For example, solid line 428 can be considered an S1-U bearer and solid line 432 can be considered an S5/S8 bearer according to LTE-EPS architecture standards. Without limitation, reference to various interfaces, such as S1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, such interface designations are combined with a suffix, e.g., a “U” or a “C” to signify whether the interface relates to a “User plane” or a “Control plane.” In addition, the core network 404 can include various signaling bearer paths/interfaces, e.g., control plane paths/interfaces represented by dashed lines 430, 434, 436, and 438. Some of the signaling bearer paths may be referred to by a specific label. For example, dashed line 430 can be considered as an S1-MME signaling bearer, dashed line 434 can be considered as an S11 signaling bearer and dashed line 436 can be considered as an S6a signaling bearer, e.g., according to LTE-EPS architecture standards. The above bearer paths and signaling bearer paths are only illustrated as examples and it should be noted that additional bearer paths and signaling bearer paths may exist that are not illustrated.

Also shown is a novel user plane path/interface, referred to as the S1-U+ interface 466. In the illustrative example, the S1-U+ user plane interface extends between the eNB 416 a and PGW 426. Notably, S1-U+ path/interface does not include SGW 420, a node that is otherwise instrumental in configuring and/or managing packet forwarding between eNB 416 a and one or more external networks 406 by way of PGW 426. As disclosed herein, the S1-U+ path/interface facilitates autonomous learning of peer transport layer addresses by one or more of the network nodes to facilitate a self-configuring of the packet forwarding path. In particular, such self-configuring can be accomplished during handovers in most scenarios so as to reduce any extra signaling load on the S/PGWs 420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown in phantom. Storage device 440 can be integral to one of the network nodes, such as PGW 426, for example, in the form of internal memory and/or disk drive. It is understood that storage device 440 can include registers suitable for storing address values. Alternatively or in addition, storage device 440 can be separate from PGW 426, for example, as an external hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to the forwarding of packet data. For example, storage device 440 can store identities and/or addresses of network entities, such as any of network nodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In the illustrative example, storage device 440 includes a first storage location 442 and a second storage location 444. First storage location 442 can be dedicated to storing a Currently Used Downlink address value 442. Likewise, second storage location 444 can be dedicated to storing a Default Downlink Forwarding address value 444. PGW 426 can read and/or write values into either of storage locations 442, 444, for example, managing Currently Used Downlink Forwarding address value 442 and Default Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for each EPS bearer is the SGW S5-U address for each EPS Bearer. The Currently Used Downlink Forwarding address” for each EPS bearer in PGW 426 can be set every time when PGW 426 receives an uplink packet, e.g., a GTP-U uplink packet, with a new source address for a corresponding EPS bearer. When UE 414 is in an idle state, the “Current Used Downlink Forwarding address” field for each EPS bearer of UE 414 can be set to a “null” or other suitable value.

In some embodiments, the Default Downlink Forwarding address is only updated when PGW 426 receives a new SGW S5-U address in a predetermined message or messages. For example, the Default Downlink Forwarding address is only updated when PGW 426 receives one of a Create Session Request, Modify Bearer Request and Create Bearer Response messages from SGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a per bearer basis, it is understood that the storage locations can take the form of tables, spreadsheets, lists, and/or other data structures generally well understood and suitable for maintaining and/or otherwise manipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 are illustrated in a simplified block diagram in FIG. 4. In other words, either or both of access network 402 and the core network 404 can include additional network elements that are not shown, such as various routers, switches and controllers. In addition, although FIG. 4 illustrates only a single one of each of the various network elements, it should be noted that access network 402 and core network 404 can include any number of the various network elements. For example, core network 404 can include a pool (i.e., more than one) of MMEs 418, SGWs 420 or PGWs 426.

In the illustrative example, data traversing a network path between UE 414, eNB 416 a, SGW 420, PGW 426 and external network 406 may be considered to constitute data transferred according to an end-to-end IP service. However, for the present disclosure, to properly perform establishment management in LTE-EPS network architecture 400, the core network, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up request between any two elements within LTE-EPS network architecture 400. The connection set up request may be for user data or for signaling. A failed establishment may be defined as a connection set up request that was unsuccessful. A successful establishment may be defined as a connection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion (e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a second portion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, and a third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426. Various signaling bearer portions are also illustrated in FIG. 4. For example, a first signaling portion (e.g., a signaling radio bearer 448) between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1 signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling, e.g., IP tunneling, by which data packets can be forwarded in an encapsulated manner, between tunnel endpoints. Tunnels, or tunnel connections can be identified in one or more nodes of network 400, e.g., by one or more of tunnel endpoint identifiers, an IP address and a user datagram protocol port number. Within a particular tunnel connection, payloads, e.g., packet data, which may or may not include protocol related information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 a between two tunnel endpoints 454 a and 456 a, and a second tunnel 452 b between two tunnel endpoints 454 b and 456 b. In the illustrative example, first tunnel 452 a is established between eNB 416 a and SGW 420. Accordingly, first tunnel 452 a includes a first tunnel endpoint 454 a corresponding to an S1-U address of eNB 416 a (referred to herein as the eNB S1-U address), and second tunnel endpoint 456 a corresponding to an S1-U address of SGW 420 (referred to herein as the SGW S1-U address). Likewise, second tunnel 452 b includes first tunnel endpoint 454 b corresponding to an S5-U address of SGW 420 (referred to herein as the SGW S5-U address), and second tunnel endpoint 456 b corresponding to an S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred to as a two tunnel solution, e.g., according to the GPRS Tunneling Protocol User Plane (GTPv1-U based), as described in 3GPP specification TS 29.281, incorporated herein in its entirety. It is understood that one or more tunnels are permitted between each set of tunnel end points. For example, each subscriber can have one or more tunnels, e.g., one for each PDP context that they have active, as well as possibly having separate tunnels for specific connections with different quality of service requirements, and so on.

An example of second tunnel solution 458 includes a single or direct tunnel 460 between tunnel endpoints 462 and 464. In the illustrative example, direct tunnel 460 is established between eNB 416 a and PGW 426, without subjecting packet transfers to processing related to SGW 420. Accordingly, direct tunnel 460 includes first tunnel endpoint 462 corresponding to the eNB S1-U address, and second tunnel endpoint 464 corresponding to the PGW S5-U address. Packet data received at either end can be encapsulated into a payload and directed to the corresponding address of the other end of the tunnel. Such direct tunneling avoids processing, e.g., by SGW 420 that would otherwise relay packets between the same two endpoints, e.g., according to a protocol, such as the GTP-U protocol.

In some scenarios, direct tunneling solution 458 can forward user plane data packets between eNB 416 a and PGW 426, by way of SGW 420. That is, SGW 420 can serve a relay function, by relaying packets between two tunnel endpoints 416 a, 426. In other scenarios, direct tunneling solution 458 can forward user data packets between eNB 416 a and PGW 426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. The number and types of bearers can depend on applications, default requirements, and so on. It is understood that the techniques disclosed herein, including the configuration, management and use of various tunnel solutions 450, 458, can be applied to the bearers on an individual bases. That is, if user data packets of one bearer, say a bearer associated with a VoIP service of UE 414, then the forwarding of all packets of that bearer are handled in a similar manner. Continuing with this example, the same UE 414 can have another bearer associated with it through the same eNB 416 a. This other bearer, for example, can be associated with a relatively low rate data session forwarding user data packets through core network 404 simultaneously with the first bearer. Likewise, the user data packets of the other bearer are also handled in a similar manner, without necessarily following a forwarding path or solution of the first bearer. Thus, one of the bearers may be forwarded through direct tunnel 458; whereas, another one of the bearers may be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine in the form of a computer system 500 within which a set of instructions, when executed, may cause the machine to perform any one or more of the methods described above. One or more instances of the machine can operate, for example, as processor 302, device 101, DNS server 223, S-CSCF 222, MME 418, SGW 420, HSS 422, PCRF 424, PGW 426 and other devices of FIG. 1 and FIG. 4. In some embodiments, the machine may be connected (e.g., using a network 502) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client user machine in a server-client user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet, a smart phone, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a communication device of the subject disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., a central processing unit (CPU)), a graphics processing unit (GPU, or both), a main memory 506 and a static memory 508, which communicate with each other via a bus 510. The computer system 500 may further include a display unit 512 (e.g., a liquid crystal display (LCD), a flat panel, or a solid state display). Computer system 500 may include an input device 514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), a disk drive unit 518, a signal generation device 520 (e.g., a speaker or remote control) and a network interface device 522. In distributed environments, the embodiments described in the subject disclosure can be adapted to utilize multiple display units 512 controlled by two or more computer systems 500. In this configuration, presentations described by the subject disclosure may in part be shown in a first of display units 512, while the remaining portion is presented in a second of display units 512.

The disk drive unit 518 may include a tangible computer-readable storage medium 524 on which is stored one or more sets of instructions (e.g., software 526) embodying any one or more of the methods or functions described herein, including those methods illustrated above. Instructions 526 may also reside, completely or at least partially, within main memory 506, static memory 508, or within processor 504 during execution thereof by the computer system 500. Main memory 506 and processor 504 also may constitute tangible computer-readable storage media.

As shown in FIG. 6, telecommunication system 600 may include wireless transmit/receive units (WTRUs) 602, a RAN 604, a core network 606, a public switched telephone network (PSTN) 608, the Internet 610, or other networks 612, though it will be appreciated that the disclosed examples contemplate any number of WTRUs, base stations, networks, or network elements. Each WTRU 602 may be any type of device configured to operate or communicate in a wireless environment. For example, a WTRU may comprise, a device 101, network device 300, or the like, or any combination thereof. By way of example, WTRUs 602 may be configured to transmit or receive wireless signals and may include a UE, a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a PDA, a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, or the like. It is understood that the exemplary devices above may overlap in their functionality and the terms are not necessarily mutually exclusive. WTRUs 602 may be configured to transmit or receive wireless signals over an air interface 614.

Telecommunication system 600 may also include one or more base stations 616. Each of base stations 616 may be any type of device configured to wirelessly interface with at least one of the WTRUs 602 to facilitate access to one or more communication networks, such as core network 606, PTSN 608, Internet 610, or other networks 612. By way of example, base stations 616 may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, or the like. While base stations 616 are each depicted as a single element, it will be appreciated that base stations 616 may include any number of interconnected base stations or network elements.

RAN 604 may include one or more base stations 616, along with other network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), or relay nodes. One or more base stations 616 may be configured to transmit or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with base station 616 may be divided into three sectors such that base station 616 may include three transceivers: one for each sector of the cell. In another example, base station 616 may employ multiple-input multiple-output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

Base stations 616 may communicate with one or more of WTRUs 602 over air interface 614, which may be any suitable wireless communication link (e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visible light). Air interface 614 may be established using any suitable radio access technology (RAT).

More specifically, as noted above, telecommunication system 600 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. For example, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) that may establish air interface 614 using wideband CDMA (WCDMA). WCDMA may include communication protocols, such as High-Speed Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected to RAN 604 may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish air interface 614 using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 may implement radio technologies such as IEEE 602.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, or the like. For example, base station 616 and associated WTRUs 602 may implement a radio technology such as IEEE 602.11 to establish a wireless local area network (WLAN). As another example, base station 616 and associated WTRUs 602 may implement a radio technology such as IEEE 602.15 to establish a wireless personal area network (WPAN). In yet another example, base station 616 and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 6, base station 616 may have a direct connection to Internet 610. Thus, base station 616 may not be required to access Internet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more WTRUs 602. For example, core network 606 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution or high-level security functions, such as user authentication. Although not shown in FIG. 6, it will be appreciated that RAN 604 or core network 606 may be in direct or indirect communication with other RANs that employ the same RAT as RAN 604 or a different RAT. For example, in addition to being connected to RAN 604, which may be utilizing an E-UTRA radio technology, core network 606 may also be in communication with another RAN (not shown) employing a GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to access PSTN 608, Internet 610, or other networks 612. PSTN 608 may include circuit-switched telephone networks that provide plain old telephone service (POTS). For LTE core networks, core network 606 may use IMS core 614 to provide access to PSTN 608. Internet 610 may include a global system of interconnected computer networks or devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP), or IP in the TCP/IP internet protocol suite. Other networks 612 may include wired or wireless communications networks owned or operated by other service providers. For example, other networks 612 may include another core network connected to one or more RANs, which may employ the same RAT as RAN 604 or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may include multi-mode capabilities. That is, WTRUs 602 may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, one or more WTRUs 602 may be configured to communicate with base station 616, which may employ a cellular-based radio technology, and with base station 616, which may employ an IEEE 802 radio technology.

FIG. 7 is an example system 400 including RAN 604 and core network 606. As noted above, RAN 604 may employ an E-UTRA radio technology to communicate with WTRUs 602 over air interface 614. RAN 604 may also be in communication with core network 606.

RAN 604 may include any number of eNBs 702 while remaining consistent with the disclosed technology. One or more eNBs 702 may include one or more transceivers for communicating with the WTRUs 602 over air interface 614. Optionally, eNBs 702 may implement MIMO technology. Thus, one of eNBs 702, for example, may use multiple antennas to transmit wireless signals to, or receive wireless signals from, one of WTRUs 602.

Each of eNBs 702 may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink or downlink, or the like. As shown in FIG. 7 eNBs 702 may communicate with one another over an X2 interface.

Core network 606, shown in FIG. 7, may include a mobility management gateway or entity (MME) 704, a serving gateway 706, or a packet data network (PDN) gateway 708. While each of the foregoing elements are depicted as part of core network 606, it will be appreciated that any one of these elements may be owned or operated by an entity other than the core network operator.

MME 704 may be connected to each of eNBs 702 in RAN 604 via an S1 interface and may serve as a control node. For example, MME 704 may be responsible for authenticating users of WTRUs 602, bearer activation or deactivation, selecting a particular serving gateway during an initial attach of WTRUs 602, or the like. MME 704 may also provide a control plane function for switching between RAN 604 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNBs 702 in RAN 604 via the S1 interface. Serving gateway 706 may generally route or forward user data packets to or from the WTRUs 602. Serving gateway 706 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for WTRUs 602, managing or storing contexts of WTRUs 602, or the like.

Serving gateway 706 may also be connected to PDN gateway 708, which may provide WTRUs 602 with access to packet-switched networks, such as Internet 610, to facilitate communications between WTRUs 602 and IP-enabled devices.

Core network 606 may facilitate communications with other networks. For example, core network 606 may provide WTRUs 602 with access to circuit-switched networks, such as PSTN 608, such as through IMS core 614, to facilitate communications between WTRUs 602 and traditional land-line communications devices. In addition, core network 606 may provide the WTRUs 602 with access to other networks 612, which may include other wired or wireless networks that are owned or operated by other service providers.

FIG. 8 depicts an overall block diagram of an example packet-based mobile cellular network environment, such as a GPRS network as described herein. In the example packet-based mobile cellular network environment shown in FIG. 8, there are a plurality of base station subsystems (BSS) 800 (only one is shown), each of which comprises a base station controller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806, 808. BTSs 804, 806, 808 are the access points where users of packet-based mobile devices become connected to the wireless network. In example fashion, the packet traffic originating from mobile devices is transported via an over-the-air interface to BTS 808, and from BTS 808 to BSC 802. Base station subsystems, such as BSS 800, are a part of internal frame relay network 810 that can include a service GPRS support nodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 is connected to an internal packet network 816 through which SGSN 812, 814 can route data packets to or from a plurality of gateway GPRS support nodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820, 822 are part of internal packet network 816. GGSNs 818, 820, 822 mainly provide an interface to external IP networks such as PLMN 824, corporate intranets/internets 826, or Fixed-End System (FES) or the public Internet 828. As illustrated, subscriber corporate network 826 may be connected to GGSN 820 via a firewall 830. PLMN 824 may be connected to GGSN 820 via a boarder gateway router (BGR) 832. A Remote Authentication Dial-In User Service (RADIUS) server 834 may be used for caller authentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred to as macro, micro, pico, femto or umbrella cells. The coverage area of each cell is different in different environments. Macro cells can be regarded as cells in which the base station antenna is installed in a mast or a building above average roof top level. Micro cells are cells whose antenna height is under average roof top level. Micro cells are typically used in urban areas. Pico cells are small cells having a diameter of a few dozen meters. Pico cells are used mainly indoors. Femto cells have the same size as pico cells, but a smaller transport capacity. Femto cells are used indoors, in residential or small business environments. On the other hand, umbrella cells are used to cover shadowed regions of smaller cells and fill in gaps in coverage between those cells.

FIG. 9 illustrates an exemplary architecture of a typical GPRS network 900 as described herein. The architecture depicted in FIG. 9 may be segmented into four groups: users 902, RAN 904, core network 906, and interconnect network 908. Users 902 comprise a plurality of end users, who each may use one or more devices 910. Note that device 910 is referred to as a mobile subscriber (MS) in the description of network shown in FIG. 9. In an example, device 910 comprises a communications device (e.g., device 102, S-CSCF 222, network device 300, any of detected devices 500, second device 508, access device 604, access device 606, access device 608, access device 610 or the like, or any combination thereof). Radio access network 904 comprises a plurality of BSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Core network 906 may include a host of various network elements. As illustrated in FIG. 9, core network 906 may comprise MSC 918, service control point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home location register (HLR) 926, authentication center (AuC) 928, domain name system (DNS) server 930, and GGSN 932. Interconnect network 908 may also comprise a host of various networks or other network elements. As illustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, an FES/Internet 936, a firewall 1038, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, for instance, depending on the type of traffic, the traffic may be separated in that voice may be sent to PSTN 934 through GMSC 922, or data may be sent to SGSN 924, which then sends the data traffic to GGSN 932 for further forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sends a query to a database hosted by SCP 920, which processes the request and issues a response to MSC 918 so that it may continue call processing as appropriate.

HLR 926 is a centralized database for users to register to the GPRS network. HLR 926 stores static information about the subscribers such as the International Mobile Subscriber Identity (IMSI), subscribed services, or a key for authenticating the subscriber. HLR 926 also stores dynamic subscriber information such as the current location of the MS. Associated with HLR 926 is AuC 928, which is a database that contains the algorithms for authenticating subscribers and includes the associated keys for encryption to safeguard the user input for authentication.

In the following, depending on context, “mobile subscriber” or “MS” sometimes refers to the end user and sometimes to the actual portable device, such as a mobile device, used by an end user of the mobile cellular service. When a mobile subscriber turns on his or her mobile device, the mobile device goes through an attach process by which the mobile device attaches to an SGSN of the GPRS network. In FIG. 9, when MS 910 initiates the attach process by turning on the network capabilities of the mobile device, an attach request is sent by MS 910 to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 was attached before, for the identity of MS 910. Upon receiving the identity of MS 910 from the other SGSN, SGSN 924 requests more information from MS 910. This information is used to authenticate MS 910 together with the information provided by HLR 926. Once verified, SGSN 924 sends a location update to HLR 926 indicating the change of location to a new SGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS 910 was attached before, to cancel the location process for MS 910. HLR 926 then notifies SGSN 924 that the location update has been performed. At this time, SGSN 924 sends an Attach Accept message to MS 910, which in turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network, corporate network 940, by going through a Packet Data Protocol (PDP) activation process. Briefly, in the process, MS 910 requests access to the Access Point Name (APN), for example, UPS.com, and SGSN 924 receives the activation request from MS 910. SGSN 924 then initiates a DNS query to learn which GGSN 932 has access to the UPS.com APN. The DNS query is sent to a DNS server within core network 906, such as DNS server 930, which is provisioned to map to one or more GGSNs in core network 906. Based on the APN, the mapped GGSN 932 can access requested corporate network 940. SGSN 924 then sends to GGSN 932 a Create PDP Context Request message that contains necessary information. GGSN 932 sends a Create PDP Context Response message to SGSN 924, which then sends an Activate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then go through RAN 904, core network 906, and interconnect network 908, in a particular FES/Internet 936 and firewall 1038, to reach corporate network 940.

FIG. 10 illustrates a PLMN block diagram view of an exemplary architecture of a telecommunications system that may be used by IP peering system disclosed herein. In FIG. 10, solid lines may represent user traffic signals, and dashed lines may represent support signaling. MS 1002 is the physical equipment used by the PLMN subscriber. For example, device 101, network device 300, the like, or any combination thereof may serve as MS 1002. MS 1002 may be one of, but not limited to, a cellular telephone, a cellular telephone in combination with another electronic device or any other wireless mobile communication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC 1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008 pair (base station) or a system of BSC/BTS pairs that are part of a larger network. BSS 1004 is responsible for communicating with MS 1002 and may support one or more cells. BSS 1004 is responsible for handling cellular traffic and signaling between MS 1002 and a core network 1010. Typically, BSS 1004 performs functions that include, but are not limited to, digital conversion of speech channels, allocation of channels to mobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012 contains a Radio Network Controller (RNC) 1014 and one or more Nodes B 1016. RNS 1012 may support one or more cells. RNS 1012 may also include one or more RNC 1014/Node B 1016 pairs or alternatively a single RNC 1014 may manage multiple Nodes B 1016. RNS 1012 is responsible for communicating with MS 1002 in its geographically defined area. RNC 1014 is responsible for controlling Nodes B 1016 that are connected to it and is a control element in a UMTS radio access network. RNC 1014 performs functions such as, but not limited to, load control, packet scheduling, handover control, security functions, or controlling MS 1002 access to core network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless data communications for MS 1002 and UE 1024. E-UTRAN 1018 provides higher data rates than traditional UMTS. It is part of the LTE upgrade for mobile networks, and later releases meet the requirements of the International Mobile Telecommunications (IMT) Advanced and are commonly known as a 4G networks. E-UTRAN 1018 may include of series of logical network components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B (eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment (UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018 including, but not limited to, a personal computer, laptop, mobile phone, wireless router, or other device capable of wireless connectivity to E-UTRAN 1018. The improved performance of the E-UTRAN 1018 relative to a typical UMTS network allows for increased bandwidth, spectral efficiency, and functionality including, but not limited to, voice, high-speed applications, large data transfer or IPTV, while still allowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012, or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012, and E-UTRAN 1018 may provide MS 1002 with access to core network 1010. Core network 1010 may include of a series of devices that route data and communications between end users. Core network 1010 may provide network service functions to users in the circuit switched (CS) domain or the packet switched (PS) domain. The CS domain refers to connections in which dedicated network resources are allocated at the time of connection establishment and then released when the connection is terminated. The PS domain refers to communications and data transfers that make use of autonomous groupings of bits called packets. Each packet may be routed, manipulated, processed or handled independently of all other packets in the PS domain and does not require dedicated network resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network 1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 in order to facilitate core network 1010 resource control in the CS domain. Functions of CS-MGW 1026 include, but are not limited to, media conversion, bearer control, payload processing or other mobile network processing such as handover or anchoring. CS-MGW 1026 may receive connections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order to facilitate network functionality. SGSN 1032 may store subscription information such as, but not limited to, the IMSI, temporary identities, or PDP addresses. SGSN 1032 may also store location information such as, but not limited to, GGSN address for each GGSN 1034 where an active PDP exists. GGSN 1034 may implement a location register function to store subscriber data it receives from SGSN 1032 such as subscription or location information.

Serving gateway (S-GW) 1036 is an interface which provides connectivity between E-UTRAN 1018 and core network 1010. Functions of S-GW 1036 include, but are not limited to, packet routing, packet forwarding, transport level packet processing, or user plane mobility anchoring for inter-network mobility. PCRF 1038 uses information gathered from P-GW 1036, as well as other sources, to make applicable policy and charging decisions related to data flows, network resources or other network administration functions. PDN gateway (PDN-GW) 1040 may provide user-to-services connectivity functionality including, but not limited to, GPRS/EPC network anchoring, bearer session anchoring and control, or IP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription data regarding MS 1002 or UE 1024 for handling calls or data sessions. Networks may contain one HSS 1042 or more if additional resources are required. Example data stored by HSS 1042 include, but is not limited to, user identification, numbering or addressing information, security information, or location information. HSS 1042 may also provide call or session establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002 enters a new network location, it begins a registration procedure. A MSC server for that location transfers the location information to the VLR for the area. A VLR and MSC server may be located in the same computing environment, as is shown by VLR/MSC server 1028, or alternatively may be located in separate computing environments. A VLR may contain, but is not limited to, user information such as the IMSI, the Temporary Mobile Station Identity (TMSI), the Local Mobile Station Identity (LMSI), the last known location of the mobile station, or the SGSN where the mobile station was previously registered. The MSC server may contain information such as, but not limited to, procedures for MS 1002 registration or procedures for handover of MS 1002 to a different section of core network 1010. GMSC server 1030 may serve as a connection to alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. User equipment may be classified as either “white listed” or “black listed” depending on its status in the network. If MS 1002 is stolen and put to use by an unauthorized user, it may be registered as “black listed” in EIR 1044, preventing its use on the network. A MME 1046 is a control node which may track MS 1002 or UE 1024 if the devices are idle. Additional functionality may include the ability of MME 1046 to contact idle MS 1002 or UE 1024 if retransmission of a previous session is required.

As described herein, a telecommunications system wherein management and control utilizing a software designed network (SDN) and a simple IP are based, at least in part, on user equipment, may provide a wireless management and control framework that enables common wireless management and control, such as mobility management, radio resource management, QoS, load balancing, etc., across many wireless technologies, e.g. LTE, Wi-Fi, and future 5G access technologies; decoupling the mobility control from data planes to let them evolve and scale independently; reducing network state maintained in the network based on user equipment types to reduce network cost and allow massive scale; shortening cycle time and improving network upgradability; flexibility in creating end-to-end services based on types of user equipment and applications, thus improve customer experience; or improving user equipment power efficiency and battery life—especially for simple M2M devices—through enhanced wireless management.

While examples of a telecommunications system in which carrier IP peering methods may be processed and managed have been described in connection with various computing devices/processors, the underlying concepts may be applied to any computing device, processor, or system capable of facilitating a telecommunications system. The various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and devices may take the form of program code (i.e., instructions) embodied in concrete, tangible, storage media having a concrete, tangible, physical structure. Examples of tangible storage media include floppy diskettes, CD-ROMs, DVDs, hard drives, or any other tangible machine-readable storage medium (computer-readable storage medium). Thus, a computer-readable storage medium is not a signal. A computer-readable storage medium is not a transient signal. Further, a computer-readable storage medium is not a propagating signal. A computer-readable storage medium as described herein is an article of manufacture. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an device for telecommunications. In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile or nonvolatile memory or storage elements), at least one input device, and at least one output device. The program(s) can be implemented in assembly or machine language, if desired. The language can be a compiled or interpreted language, and may be combined with hardware implementations.

The methods and devices associated with a telecommunications system as described herein also may be practiced via communications embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, or the like, the machine becomes an device for implementing telecommunications as described herein. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique device that operates to invoke the functionality of a telecommunications system.

While a telecommunications system has been described in connection with the various examples of the various figures, it is to be understood that other similar implementations may be used or modifications and additions may be made to the described examples of a telecommunications system without deviating therefrom. For example, one skilled in the art will recognize that a telecommunications system as described in the instant application may apply to any environment, whether wired or wireless, and may be applied to any number of such devices connected via a communications network and interacting across the network. Therefore, a telecommunications system as described herein should not be limited to any single example, but rather should be construed in breadth and scope in accordance with the appended claims.

In describing preferred methods, systems, or apparatuses of the subject matter of the present disclosure—enabling IP peering in view of carrier ENUM—as illustrated in the Figures, specific terminology is employed for the sake of clarity. The claimed subject matter, however, is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose. In addition, the use of the word “or” is generally used inclusively unless otherwise provided herein.

This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between exemplary methods disclosed herein). Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims. 

What is claimed:
 1. A network device comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising: receiving a query associated with a connection of a first device on a first carrier network of a voice over internet protocol (IP) connection with a second device on a second carrier network, wherein the query comprises tElephone NUmber Mapping (ENUM) query with an indication of a telephone number associated with the second device, wherein the second carrier network is not trusted by the first carrier network; determining that the indication of the telephone number is not of the first carrier network; and responsive to determining that the indication of the telephone number is not of the first carrier network, based on matching a number range, providing an arpa based fully qualified domain name (FQDN) to an external routing function to route the call to a destination network.
 2. The network device of claim 1, wherein the external routing function comprises a breakout gateway control function (BGCF).
 3. The network device of claim 1, wherein the indication of the telephone number comprises an E.164 number.
 4. The network device of claim 1, wherein the network device comprises a private ENUM database.
 5. The network device of claim 1, wherein the FQDN is an entry in a private domain name system (DNS) server.
 6. A network device comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising: detecting an initiation by a first device on a first carrier network of a voice over internet protocol (IP) connection with a second device on a second carrier network, wherein the second carrier network is not trusted by the first carrier network; sending a query for a connection information to a private tElephone NUmber Mapping (ENUM) database, wherein the query comprises an indication of a telephone number; and responsive to the query, receiving an arpa based first fully qualified domain name (FQDN), wherein the first FQDN indicates the indication of the telephone number is not of the first carrier network, and wherein the first FQDN indicates an external routing function for routing the indication of a telephone number based on the number range.
 7. The network device of claim 6, wherein the external routing function comprises a breakout gateway control function (BGCF).
 8. The network device of claim 6, wherein the network device comprises a serving call session control function.
 9. The network device of claim 6, wherein the number range comprises a plurality of numbers associated with numbering plan area (NPA) or country code.
 10. The network device of claim 6, wherein the first FQDN is an entry in a private domain name system (DNS) server.
 11. The network device of claim 6, the operations further comprising sending a domain name query to a private domain name system (DNS) server to resolve the first FQDN.
 12. The network device of claim 6, the operations further comprising: sending a domain name query to a private domain name system (DNS) server to resolve the first FQDN; and receiving an internet protocol address of the first FQDN.
 13. The network device of claim 6, the operations further comprising: sending a domain name query to a private domain name system (DNS) server to resolve the first FQDN; receiving an internet protocol address of the first FQDN; and based on the internet protocol address, routing the voice over IP connection to the BGCF.
 14. A method comprising: detecting, by a network device, an initiation by a first device on a first carrier network of a voice over internet protocol (IP) connection with a second device on a second carrier network, wherein the second carrier network is not trusted by the first carrier network; sending a query, by the network device, for a connection information to a private tElephone NUmber Mapping (ENUM) database, wherein the query comprises an indication of a telephone number; and responsive to the query receiving, by the network device, a first fully qualified domain name (FQDN); mapping, by the network device, the first FQDN to a second FQDN, wherein the first FQDN indicates the indication of the telephone number is not of the first carrier network, and wherein the second FQDN indicates an external routing function for routing the indication of a telephone number based on the number range, wherein the number range indicates a plurality of telephone numbers between a first telephone number and a second telephone number.
 15. The method of claim 14, further comprising: sending a domain name query to a private domain name system (DNS) server to resolve the second FQDN; receiving an internet protocol address of the second FQDN; and based on the internet protocol address, routing the voice over IP connection to the BGCF.
 16. The method of claim 14, wherein the external routing function comprises a breakout gateway control function (BGCF).
 17. The method of claim 14, wherein the network device comprises a serving call session control function.
 18. The method of claim 14, wherein the indication of the telephone number comprises an E.164 number.
 19. The method of claim 14, wherein the network device comprises a serving call session control function.
 20. The method of claim 14, wherein the second FQDN is an entry in a private domain name system (DNS) server. 